Right object acquisition method and system

ABSTRACT

A batch rights objects (ROs) acquisition method and system is provided to enable a mobile terminal to acquire multiple rights objects in a batch processing manner. A rights object acquisition method according to an embodiment of the present invention includes transmitting a rights object request message requesting one or more rights objects of content objects from a mobile terminal to a rights issuer; creating, at the rights issuer, a rights object response message containing at least one of rights objects indicated by the rights object request message and at least one signature in response to the rights object request message; and transmitting the rights object response message from the rights issuer to the mobile terminal.

CROSS-REFERENCE TO RELATED APPLICATION(S) AND CLAIM OF PRIORITY

The present invention claims priority to an application entitled “RIGHTSOBJECT ACQUISITION METHOD AND SYSTEM” filed in the Korean IntellectualProperty Office on Jun. 9, 2007 and assigned Serial No. 2007-0056400,the contents of which are incorporated herein by reference.

TECHNICAL FIELD OF THE INVENTION

The present invention relates to a Digital Right Management (DRM) systemfor use with mobile terminals and, in particular, to a batch rightsobjects (ROs) acquisition method and system which enables a mobileterminal to acquire multiple rights objects in a batch processingmanner.

BACKGROUND OF THE INVENTION

With the widespread use of Internet and advances of the multimedia andcommunication technologies, various digital contents are distributed andacquired over the network. However, without copyright protection policy,the advanced network environment and technologies are likely to be usedfor illegal distributions of the contents.

Digital Rights Management (DRM) systems have been developed to preventthe illegal use and distribution of the copyrighted contents. DRM is aterm that refers to access control technologies for protecting thecopyrights of the authors and the content providers.

The DRM is specified to provide a controlled consumption of digitalcontents and to protect the intellectual property right of the authorsand the content providers.

Typically, encrypted DRM contents can be freely accessed and downloaded.In order to use the DRM contents, however, a license called RightsObject (RO) is required for decoding the encrypted DRM contents. Withits efficient usage control, DRM is used by many copyright holders.

DRM technologies attempt to protect the digital contents through all thephases of creation, distribution, use, and abrogation; and restrictsaccess and usage rights of the user on the digital contents. DRM allowsthe user having a valid encryption key such as RO to decode theencrypted digital content such that the digital content can be protectedeven when being illegally distributed.

The RO is a container used in the OMA DRM system, which is an open DRMstandard invented by the Open Mobile Alliance (OMA), for carrying thelicense key to decrypt the corresponding DRM contents. The RO is issuedby a Right Issuer (RI) and purchased by the end user. Since the digitalcontent and corresponding RO are delivered in a detached manner, theusage of the downloaded content is restricted to the user who acquiredthe corresponding RO.

The RO is a collection of Permission, Constraints, and other attributesthat define under what circumstances access is granted to, and whatusages are defined for, DRM content object. Typically, the usageconstraints include Count, DateTime, Interval, Timed-Count, Accumulated,and Individual. The constraints are stored in a specific field of theRO.

For example, the RO may specify the usage for an MP3 file with the countconstraint value set to “10”. In this case, the MP3 file can be played10 times and the count is decremented by 1 whenever the MP3 file isplayed. If the count value becomes “0”, the usage right on the MP3 fileexpires. In order to maintain the usage right on the MP3 file, thecorresponding RO should be updated.

FIG. 1 is a diagram illustrating RO delivery procedure in a conventionalDRM system.

In FIG. 1, a mobile terminal 101 transmits a content request message(105) to content server 102, and the content server 102 transmits acorresponding content 106 in response to the content request message105. In a case that the requested content is a DRM protected content,the content is encrypted with an encryption key and scheme specified bythe DRM and transmitted in a DRM format having the constraints (e.g.,usage rule, the number of times to be played, and duration). If a userrequest for acquiring the license to the downloaded content is detected,the mobile terminal 101 transmits a license request message 107 to aRight Issuer (RI) 103, and the RI 103 transmits the correspondinglicense 108 to the mobile terminal 101 in response to the licenserequest message. Here, the license is a usage right on the content whichincludes a decryption key and usage constraint information. In the caseof DRM content object, the mobile terminal 101 should acquire the usageright for consuming the content. Accordingly, the RI 103 checks whetherthe identity of the user of the mobile terminal 101 is valid. If it isdetermined that the user is valid, the RI 103 transmits the license tothe mobile terminal 101. If the license is received from the RI 103, themobile terminal 101 can play the content using the license. Typically,the decryption key and usage constraint information is extracted fromthe license by a DRM client application installed in the mobile terminal101. The content is decrypted by using the decryption key and playedunder the usage constraints specified in the license.

However, the conventional DRM system has a drawback in that the ROacquisition or update process is performed item by item such that it istime consuming and cumbersome to acquire or update multiple ROs. Thatis, since the ROs required for consuming DRM content objects arepurchased one by one, the user should perform the purchasing processrepeatedly as many as the number of the DRM content objects, resultingin user inconvenience.

For example, when it is decided to update the expired usage rights on aMP3 file, a video file, and a game file, the user should purchase theROs of the MP3, video, and game files one by one through respectivepurchase transactions. These repeated RO purchase transactions aretime-consuming and cumbersome, resulting in contents managementinefficiency and user inconvenience.

SUMMARY OF THE INVENTION

To address the above-discussed deficiencies of the prior art, it is aprimary object of the present invention to provide a batch ROacquisition method and system of a mobile terminal that that is capableof acquiring and updating multiple ROs through a simplified process.

Also, the present invention provides a batch RO acquisition method andsystem of a mobile terminal that is capable of improving protectedcontents management efficiency by acquiring multiple ROs in a batchprocessing manner.

Also, the present invention provides a batch RO acquisition method andsystem of a mobile terminal that is capable purchasing andauthenticating multiple ROs in a batch processing manner by introducinga broker server.

In accordance with an exemplary embodiment of the present invention, arights object acquisition method includes transmitting a rights objectrequest message requesting one or more rights objects of content objectsfrom a mobile terminal to a rights issuer; creating, at the rightsissuer, a rights object response message containing at least one ofrights objects indicated by the rights object request message and atleast one signature in response to the rights object request message;and transmitting the rights object response message from the rightsissuer to the mobile terminal.

In accordance with another exemplary embodiment of the presentinvention, a rights object acquisition method includes transmitting arights object request message requesting one or more rights objects ofcontent objects from a mobile terminal to a first rights issuer;creating, at the first rights issuer, a first rights object responsemessage containing at least one of rights objects indicated by therights object request message and at least one signature; transmittingthe rights object request message and the first rights objects responsemessage from the first rights issuer to a second rights issuerdesignated in the rights object request message; creating, at the secondrights issuer, a second rights object response message containing atleast one of rights objects indicated by the rights object requestmessage and at least one signature; and transmitting, when no otherrights issuer designated in the rights object request message remains,the second rights object response message from the second rights issuerto the mobile terminal.

In accordance with another exemplary embodiment of the presentinvention, a rights object acquisition method includes transmitting arights object request message requesting one or more rights objects ofcontent objects from a mobile terminal to a first rights issuer;transmitting the rights object request message from the first rightsissuer to a second rights issuer designated in the rights object requestmessage; transmitting a rights object response message containing atleast one of the rights objects indicated by the rights object requestmessage and the first rights issuer's signature from the first rightsissuer to the mobile terminal; and transmitting a right object responsemessage containing at least one of the rights objects indicated by therights object request message and the first rights issuer's signaturefrom the first rights issuer to the mobile terminal.

In accordance with another exemplary embodiment of the presentinvention, a rights object acquisition system includes a mobile terminalwhich requests and acquires at least one rights object of at least onecontent object in a batch processing manner; and a server which performsauthentication of the mobile terminal and provides the mobile terminalwith the at least one rights objects in a batch processing manner.

Before undertaking the DETAILED DESCRIPTION OF THE INVENTION below, itmay be advantageous to set forth definitions of certain words andphrases used throughout this patent document: the terms “include” and“comprise,” as well as derivatives thereof, mean inclusion withoutlimitation; the term “or,” is inclusive, meaning and/or; the phrases“associated with” and “associated therewith,” as well as derivativesthereof, may mean to include, be included within, interconnect with,contain, be contained within, connect to or with, couple to or with, becommunicable with, cooperate with, interleave, juxtapose, be proximateto, be bound to or with, have, have a property of, or the like.Definitions for certain words and phrases are provided throughout thispatent document, those of ordinary skill in the art should understandthat in many, if not most instances, such definitions apply to prior, aswell as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumerals represent like parts:

FIG. 1 is a diagram illustrating RO delivery procedure in a conventionalDRM system;

FIG. 2 is a block diagram illustrating a configuration of a mobileterminal according to an exemplary embodiment of the present invention;

FIG. 3 is a message flow diagram illustrating a batch DRM-RO acquisitionmethod according to an exemplary embodiment of the present invention;

FIG. 4 is a diagram illustrating a structure of DCF for use in a batchRO acquisition method according to an exemplary embodiment of thepresent invention;

FIG. 5 is a message flow diagram illustrating a batch DRM-RO acquisitionmethod according to another exemplary embodiment of the presentinvention;

FIG. 6 is a schematic diagram illustrating a batch DRM-RO acquisitionsystem according to an exemplary embodiment of the present invention;

FIG. 7 is a message flow diagram illustrating a batch RO acquisitionmethod according to another exemplary embodiment of the presentinvention;

FIG. 8 is a schematic block diagram illustrating a batch RO acquisitionsystem according to another exemplary embodiment of the presentinvention; and

FIG. 9 is a schematic block diagram illustrating an aggregation ROacquisition system according to another exemplary embodiment of thepresent invention.

DETAILED DESCRIPTION OF THE INVENTION

FIGS. 2 through 9, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged communication system.

In the present invention, a Rights Object (RO) acquisition method andsystem is provided. The RO acquisition method and system of the presentinvention enables a mobile terminal to acquire ROs for multiple DigitalRights Management (DRM) protected content items in an aggregationmanner. In the RO acquisition method system according to the presentinvention, the management processes such as content purchase, ROacquisition and update, and authentication are performed by means of abroker server. In the following, the term “RO acquisition” is used inthe meaning including “RO update” in order to simplify the explanation.

In the following, the mobile terminal can be one of the various kinds ofdevices including cellular phones supporting data and voicecommunications according to various radio communication standards,Portable Multimedia Player (PMP), MP3 player, Digital BroadcastReceiver, Personal Digital Assistant (PDA), laptop and desktop computer,and their equivalents supporting a wired or wireless communication.

FIG. 2 is a block diagram illustrating a configuration of a mobileterminal according to an exemplary embodiment of the present invention.Although a mobile phone is depicted as the mobile terminal in FIG. 2,the present invention is not limited to the mobile phone.

As shown in FIG. 2, the mobile terminal 200 includes a radio frequency(RF) unit 210, a data processing unit 220, an audio processing unit 230,an input unit 240, a memory unit 250, a display unit 260, and a controlunit 270.

Referring to FIG. 2, the RF unit 210 is responsible for radiocommunication of the mobile terminal 200. The RF unit 210 establishes aradio communication channel with a communication system according to aspecific communication scheme. Particularly, the RF unit 210 allows themobile terminal 200 to exchange control messages with a web server foracquiring the contents and their ROs. The RF unit 210 includes an RFtransmitter for up-converting and amplifying the transmission signalsand an RF receiver for low-noise amplifying and down-converting thereceived signals.

The RF unit 210 allows the mobile terminal 200 to download DRM contentsfrom a contents server and ROs required for playing the DRM contentsfrom a Rights Issuer (RI) or a Broker server. The RF unit 210 transmitsa Right Object Acquisition Protocol (ROAP) Trigger Request and RORequest messages to the RI or Broker server and receives ROAP Triggermessage and RO Response message. These messages are described in moredetail later.

The data processing unit 220 is responsible for processing voice datainput by the audio processing unit 230, text data input through theinput unit 240, and the data incoming from and outgoing to the RF unit210. The data processing unit 220 may include a modem and a codec. Thecodec includes a data codec for processing packet data and an audiocodec for processing audio data.

The audio processing unit 230 processes the audio signal output by thedata processing unit 220 so as to output the audio signal through aspeaker (SPK) in the form of audible sound and processes the audiosignal input through a microphone (MIC) so as to output the processedaudio signal to the data processing unit 220. The audio processing unit230 outputs audio data including voice data through the speaker (SPK) inthe form of audible sound and outputs the audio signal including voiceinput through the microphone (MIC) to the data processing unit 220 inthe form of audio data.

Particularly, the audio processing unit 230 is configured to play theaudio data contained in the DRM contents selected by a user.

The input unit 240 receives various alphanumeric key inputs and functionkey inputs for configuring and controlling functions of the mobileterminal 200 and transfers the key sequences corresponding to the keyinputs to the control unit 270. The input unit 240 can be implementedwith at least one of a touchpad, a normal keypad, a touchscreen, aqwerty keyboard, and specific types of function keys. Particularly, theinput unit 240 generates a key signal for selecting an item listed on alist (DRM contents list or ROs list by content item) displayed on thedisplay unit 260 and transfers the key signal to the control unit 270.Of course, multiple items can be selected from the list in response tothe user's requests.

The memory unit 250 stores at least one application for executingfunctions associated with the RO acquisition method and user datacollected from external devices (contents server, RI, Broker server, andanother mobile terminal). The user data include phonebook data, stilland motion picture files, audio files, other types of digital contents,DRM-protected contents, and RO. The application can be a programassociated with playback of the user data. Particularly, the applicationcan be a content management program for managing and controlling the useof DRM-protected contents. The memory unit 250 may include at least onebuffer for buffering user data generated during the operation of theapplication.

The memory unit 250 stores at least one kind of content informationassociated with each DRM content object. The content informationincludes a size, a data type, a title, a playable period, a playablenumber of times, content-related information, a usage restriction, etc.Particularly, the memory unit stores ROs of each DRM content object.

The display unit 260 displays screens representing the data generated bythe application and key manipulation status and preset functioninformation. The display unit 260 can be implemented with a LiquidCrystal Display (LCD). The LCD may have touchscreen functionality. Inthis case, the display unit 260 operates as a part of the input unit240.

The control unit 270 controls general operations of the mobile terminal200 and signaling among the internal components of the mobile terminal200. The control unit 270 controls interoperation of the data processingunit 220, audio processing unit 230, input unit 240, memory unit 250,and display unit 260. The control unit 270 may include the dataprocessing unit 220.

Particularly, the control unit 270 controls package purchase of multipleDRM contents items and batch RO acquisition for the DRM contents items.The control unit 270 also controls display of the DRM contents itemlist, presentation of the items selected from the DRM contents itemlist, and purchase information of the DRM contents items and ROs. Thecontrol unit 270 also controls generation of the ROAP Trigger Requestmessage and RO Request message.

Although the configuration of the mobile terminal is schematicallydepicted in FIG. 2, the present invention is not limited thereto. Forexample, the mobile terminal 200 may further include at least one ofcamera module, electric settlement module, Bluetooth module, batterymodule, and digital broadcast receiver module, and other optionalfunction modules. Also, any of the internal components constituting themobile terminal may be omitted or replaced with an equivalent functionalcomponent according to the functional design of the mobile terminal.

Now, a method for acquiring ROs of DRM contents items (called DRM-ROhereinafter) is described with reference to the operation of the abovestructured mobile terminal.

FIG. 3 is a message flow diagram illustrating a batch DRM-RO acquisitionmethod according to an exemplary embodiment of the present invention.

Referring to FIG. 3, if an RO acquisition command is input for acquiringROs, the mobile terminal 200 generates an ROAP Trigger Request messageand sends the ROAP Trigger Request message to the RI 250 (S301). TheROAP Trigger Request message includes at least one content identifier(CID). The ROAP Trigger Request message also includes a deviceidentifier (DeID) of the mobile terminal 200 and at least one constraintfor restricting the usage rights of at least one DRM content object.

In a case that a parent license of at least two child licenses exists,the ROAP Trigger Request message may further includes parent licenseinformation. For example, in order to acquire two ROs for a track 1 anda track 3 dependent on a music album A, the ROAP Trigger Request messagemay include an identifier of the music album A in addition to theidentifiers of the track 1 and track 3. In this case, the ROs for thetrack 1 and track 3 can be acquired only with the RO for the album Aafterward.

By constraining the play permissions of the track 1 and track 3 with aparent RO, either track 1 and track 3 can be played up to a total usagetimes restricted by a constraint of the parent RO.

Also, different parent licenses can be applied. For example, the usermay create a content list (e.g., my list and favorite list) as a parentgroup. In this case, the ROs of the content items listed in the contentlist are dependent on a group rights object for the content list.

The DRM content object can be a content item that is received fromanother device (for example, another terminal or server) but has notacquired corresponding RO or of which RO has expired.

The mobile terminal 200 selects an RI for purchasing an RO of at leastone DRM content object with reference to an RI's Uniform ResourceLocation (URL) information contained in the header information of theDRM content object. The ROAP Trigger Request message is sent to the RIURL.

In this embodiment, a DRM Content Format (DCF) having an additionalfield indicating the address of the RI is proposed for acquiringmultiple ROs in an aggregate manner.

FIG. 4 is a diagram illustrating a structure of DCF for use in a batchRO acquisition method according to an exemplary embodiment of thepresent invention.

In FIG. 4, a BatchRIURL 410 is an address of RI which supports a batchRO acquisition, and a BatchRIURLLength 420 indicates a length of theBatchRIURL 410. The batch RI information field is added to the CommonHeader of the DCF as a mandatory field or as an extended header fieldwhich is one of mandatory fields contained in the common header.

Returning to FIG. 3, the mobile terminal 200 selects an RI for acquiringthe ROs for at least one DRM contents item with reference to the RI URLaddress previously stored in the memory unit 250 and attempts to accessthe RI. Also, the mobile terminal 200 can request a Batch RI URL foracquiring the DRM ROs to the RI 250 and attempts to access the RI URLresponded by the RI 250. The RI URL received from the RI 250 is storedand used for acquiring the ROs later in an aggregate manner.

If the ROAP Trigger Request message is received, the RI 250 generates anROAP Trigger message and sends the ROAP Trigger message to the mobileterminal 200 (S303). The ROAP Trigger message may include priceinformation on the ROs of the content items indicated by the ROAPTrigger Request message. Also, the ROAP Trigger message includes one ormore roIDs to identify the ROs corresponding to the content items. TheROAP trigger message may include at least one of roapURL, RI ID, RIAlias, Domain ID, Domain Alias, and Nonce.

The ROAP Trigger request message and ROAP Trigger message can be sent inthe form a HTTP GET or a HTTP POST (see RO acquisition mechanism of OMADRM v2.0). In a group RO acquisition method for acquiring multiple ROssimultaneously, the message length may increase, whereby HTTP POSTprefers to send the ROAP messages.

If the ROAP Trigger message is received, the mobile terminal 200displays information on the purchase prices of the ROs of the DRMcontents items on the display unit with reference to the informationcontained in the ROAP trigger message.

Next, the mobile terminal 200 generates a RO Request message andtransmits the RO Request message to the RI 250 (S305). At this time, theDRM content objects indicated by the RO Request message may be identicalwith those indicated by the ROAP Trigger Request message or not. Thatis, the list of ROs can be modified by the user.

If the RO Request message is received, the RI 250 issues the ROsindicated by the RO Request message and transmits an RO Response message(S307) containing the ROs to the mobile terminal 200.

Upon receiving the RO Response message, the mobile terminal 200 extractsROs from the RO Response message so as to acquire multiple ROs in anaggregate manner.

The RO Response may further include a session ID for establishing asession between the RI 250 and the mobile terminal 200 so as to checkwhether the RO acquisition is successfully.

In this case, the mobile terminal 200 establishes a session with the RI250 on the basis of the session ID and transmits an RO Confirm Requestmessage to the RI 250 in the session. The RO Confirm Request messageincludes a parameter such as RO Confirm Info for indicating thesuccessful RO acquisition.

In the RO Confirm Request message is received, the RI 250 ends the ROacquisition procedure or retransmits the ROs on the basis of RO ConfirmInfo. If it is determined that the multiple ROs are successfullydelivered, the RI 250 transmits an RO Confirm Response message to themobile terminal 200.

In addition to the steps of FIG. 3, the mobile terminal 200 may performa web transaction with the RI 250 after transmitting the ROAP TriggerRequest message. At this time, the permissions and constraints on theuse of DRM contents can be negotiated. For example, the RI 250 publishespurchase prices information of the content items listed in the ROAPTrigger Request message, and the mobile terminal transmits theinformation on the content items that are finally confirmed by the userto the RI 250. If the web transaction is completed by the final userconfirmation, the RI 250 may transmit a ROAP Trigger message listing thecontent items to be delivered to the mobile terminal 200.

The batch RO acquisition can be implemented without adding theBatchRIURL field to the DCF structure.

FIG. 5 is a message flow diagram illustrating a batch DRM-RO acquisitionmethod according to another exemplary embodiment of the presentinvention. In this embodiment, the BatchRIURL is not provided in the DCFstructure, but, each content item has the URL of RI delivered thecontent item.

Referring to FIG. 5, if a batch RO acquisition command is input by theuser, the mobile terminal 200 generates a ROAP Trigger Request messagecontaining CIDs of individual DRM content objects and sends the ROAPTrigger Request message to the RI 250. Here, the mobile terminal 200sends the ROAP Trigger Request message (S501) to the RI 250 withreference to an RI URL of one of multiple DRM content objects.

If the RI 250 received the ROAP Trigger Request message has no group ROtransmission capability, the RI 250 sends a Redirection messagenotifying a new URL of another RI, which has the group RO transmissioncapability, to the mobile terminal 200 (S503). The Redirection messagecan be one of HTTP 302, HTTP 303, and HTTP 307 messages proposed in OMADRM.

If the Redirection message is received, the mobile terminal 200transmits the ROAP Trigger Request message to the RI 300 indicated bythe RI URL contained in the Redirection message (S505). Accordingly, themobile terminal 200 acquires the ROs from the RI 300 in an aggregationmanner.

As described above, the batch RO acquisition method according to anexemplary embodiment of the present invention allows the mobile terminalto acquire multiple ROs in the aggregation manner through a signalpurchase procedure, resulting in improving user convenience.

A multi-RI involved batch RO acquisition method, in which individual ROsare acquired from different RIs in a batch manner, is describedhereinafter.

FIG. 6 is a schematic diagram illustrating a batch DRM-RO acquisitionsystem according to an exemplary embodiment of the present invention.

As shown in FIG. 6, a batch DRM-RO acquisition system according to anembodiment of the present invention includes a mobile terminal 200, aplurality of RIs 610 to 630, and a Broker server 400 located between themobile terminal 200 and the arbitrary number of RIs.

The Broker server 400 acts as a signal service point for managingprocesses associated with RO acquisition (message generation andexchange, authentication, and digital signature, etc.). The brokerserver-involved batch RO acquisition procedure is described hereinafterin more detail with reference to FIG. 7.

FIG. 7 is a message flow diagram illustrating a batch RO acquisitionmethod according to another exemplary embodiment of the presentinvention.

Referring to FIG. 7, if an RO acquisition command is input, the mobileterminal 200 generates an ROAP Trigger Request message containing a CIDlist listing CIDs of DRM content objects indicated by the RO acquisitioncommand and transmits the ROAP Trigger Request message to the brokerserver 400 (S701). The ROAP Trigger Request message is structuredidentically with those of the other embodiments depicted in FIGS. 3 and5. The ROAP Trigger Request message may further include RI URLs of theRIs 610 to 630 that provide the the respective content objects indicatedby the CIDs.

If the ROAP Trigger Request message is received, the broker server 400extracts the CIDs of the content objects from the ROAP Trigger Requestmessage by RI URL and generates new ROAP Trigger Request messagesdestined to the RIs 610 to 630 corresponding to the respective RI URLs.Next, the broker server 400 transmits the new ROAP Trigger Requestmessages to the corresponding RIs 610 to 630 (S703). At this time, eachnew ROAP Trigger Request message contains at least one CID of thecontent object provided by the RI to which it is destined.

Each of the RIs 610 to 630 receives only the new ROAP Trigger Requestmessage having its RI URL. In response to the new ROAP Trigger Requestmessage, each RI transmits an ROAP Trigger message to the broker server400 (S705). The ROAP trigger message contains purchase information onthe content objects indicated by the CIDs listed on the CID list ofextracted from the new ROAP Trigger Request message. The ROAP triggermessages are structured identically with those of the embodimentsdepicted in FIGS. 3 and 5.

The broker server 400 receives the ROAP Trigger messages transmitted bythe RIs 610 to 630 and transmits a new ROAP Trigger message containingtotal purchase information to the mobile terminal 200 (S707). The totalpurchase information is created by packaging the purchase informationextracted from the ROAP Trigger messages received from the respectiveRIs.

If the new ROAP Trigger message is received, the mobile terminal 200displays the total purchase information extracted from the ROAP Triggermessage on the display unit. Next, the mobile terminal 200 generates anRO Request message containing CIDs of the content objects which isfinally decided by the user and transmits the RO Request message to thebroker server 400 (S709). The CID list of the ROAP Trigger Requestmessage may be identical with or different from the CID list of the RORequest message. That is, the the CIDs listed on the CID list of theROAP Trigger Request message can be changed by the user's finaldecision. In FIG. 7, it is assumed that the CIDs of the DRM contentobjects to purchase are changed in the RO Request message. The RORequest message transmitted by the mobile terminal 200 is formatted asshown in Table 1.

If the RO Request message is received, the broker server 400 transmitsthe RO Request message to at least one of the RIs 610 to 630 accordingto the RI URLs indicated by the RO request message (S711). At this time,the RIs as destination of the RO Request message are determined by theCIDs of the content objects that are finally decided to be purchased bythe user. That is, the broker server 400 extracts the CIDs from the RORequest message transmitted by the mobile terminal 200 and generatesindividual new RO Request messages destined to the respective RIs. Thenew request message transmitted by the broker server 400 is formatted asshown in Table 1.

In FIG. 7, the RIs 610 and 620 are determined as the destinations of thenew RO Request messages due to the change of content objects to bepurchased. The broker sever 400 may authenticate the mobile terminal 200using the RO Request message transmitted by the mobile terminal 200. Theauthentication may be performed at the initial connection of the mobileterminal and skipped from then.

Both the RO Request messages transmitted by the mobile terminal 200 andthe broker server 400 are structured in the following format of Table 1.

TABLE 1 <element name=″roRequest” type=”roap:RORequest”/>  <complexTypename=”RORequest”>   <annotation>    <documentation xml :lang=″en“>   Message sent from Device to RI to request an RO.    </documentation></annotation> <complexContent>   <extension base=”roap:Request”>   <sequence>     <element name=”devicelD” type=″roap:Identifier”>    <element name=”domainID” type=″roap:DomainIdentifier”minOccurs=”0”/>     <element name~″ riID″ type=″roap:Identifier”/>    <element name=″nonce″ type=″roap:Nonce”/>     <element name=″time″type=″dateTime″/>     <element name= “roInfo”>      <complexType>      <sequence maxOccurs=”unbounded”>       <element name=″roID″type=″ID″/>       <element name=″ dcfHash” minOccurs=″0″>     <complexType>        <sequence>         <element name=″hash”type=”base64Binary”/>        </sequence>        <attributename=″algorithm″ type=”anyURI”         default=http://wwvv.w3.org/2000/09/xmldsig#          sha1/>       </complexType>       </element>      </sequence>     </complexType>     </element>     <element name=″certificateChain″type=″roap:CertificateChain″ minOccurs=″0″/>     <elementname=″extensions″ type=″roap:Extensions″ mninOccurs=″0”/>     <elementname=″signature” type=”base64Binary”/>    </sequence>   </extension> </complexContent> </complexType>

As shown in Table 1, the RO Request message according to an exemplaryembodiment of the present invention includes at least one of parameterssuch as device ID (deviceID), domain ID (domainID), RI ID (riID),nounce, time, RO information (roInfo), certification chain(certificateChain), extensions, and signature. The nonce element is aparameter generated randomly. The signature element is a digitalsignature of the mobile terminal and it is included in the RO Requestmessage for verifying the mobile terminal.

The RIs 610 and 620 received the RO Request messages verify the contentobject on the basis of the RO Request message. Next, each of the RIs 610and 620 generates ROs indicated by the RO Request message and transmitsa RO Response message containing the ROs to the broker server 400(S713). The RO Response message transmitted by the RI is formatted asshown in Table 2.

Upon receiving the RO Response messages from the RIs 610 and 620, thebroker server 400 extracts the ROs from the RO Response messages. Thebroker server 400 performs batch processing of the digital signaturesfor inter-authentication between the mobile terminal 200 and the RIs 610and 620 and then transmits a new RO Response message generated withreference to the RO Response messages received from the RIs 610 and 620to the mobile terminal 200 (S715). The RO Response message transmittedby the broker server 400 is formatted as shown in Table 2.

The broker server 400 can verify a public key certificate of the mobileterminal 200 using an Online Certificate Status Protocol (OCSP). TheOCSP is a protocol to verify a public key certificate of the mobileterminal 200 in real time. That is, the OCSP checks whether the publickey certificate of the mobile terminal is aborted. Also, a CertificateRevocation List (CRL) can be used.

The broker server 400 can verify the validity of the public keycertificate of the mobile terminal 200 using the OCSP in an initialregistration process. Also, public key certificate verification can beperformed in response to the request of the broker server 400 or RIs 610to 630. For example, in a case that a DRM time (a secure time) of aspecific content object is not matched with the time of RI (i.e., thedifference of the DRM time and the local time of RI or broker server 400is greater than a threshold value) in the DRM-RO acquisition procedure,the public key certificate of the mobile terminal 200 can be verified.The verification on the public key certificate of the broker server orRI can be performed by exchanging the OCSP Request and OCSP Responsemessages with an OCSP responder.

The mobile terminal 200 received the RO Response message from the brokerserver 400 extracts the ROs contained in the RO Response message so asto acquire the ROs of the DRM contents in an aggregate manner.

The RO Response message transmitted by the RIs 610 to 630 or the brokerserver 400 is structured in the following format of Table 2.

TABLE 2 <element name=“roResponse” type=“roap:ROResponse”/> <complexTypename=”ROResponse”> <annotation>  <documentation xml:lang=“en” >  Messagesent from RI to Device in response to a roRequest message. </documentation> </annotation> <complexContent>  <extensionbase=“roap:Response”>   <sequence minOccurs=“0”>    <elementname=“deviceID” type=“roap:Identifier”/>    <element name=“rilD”type=“roap:Identifier”/>    <element name=“nonce” type=“roap:Nonce”minOccurs=“0”/>    <element name=“protectedRO” type=“roap:ProtectedRO”      maxOccurs=“unbounded”/>    <element name=“certificateChain”type=“roap:CertificateChain” minOccurs=“0”/>    <elementname=“ocspResponse” type=“base64Binary”       minOccurs=“0”maxOccurs=“unbounded”/>    <element name=“extensions”type=“roap:Extensions” minOccurs=“0”/>    <element name=“signature”type=“base64Binary”/>   </sequence>     <attribute name=“algorithm”type=“anyURL”        default=http://www.w3.org/2000/09/xmldsig #sha1/>  </extension>  </complexContent> </complexType>

As shown in Table 2, the RO Response message according to an exemplaryembodiment of the present invention includes at least one of parametersuch as deviceID, riID, nonce, protectedRO, certificateChain,ocspResponse, and signature. The RO Response transmitted by the brokerserver may further include a broker server ID (brokerID). The brokerIDcan be replaced by the riID. The nonce element is a random valuedesignated by the RI and can be omitted. The signature element is adigital signature of the RI and it can be used in the authenticationprocedure. The protected RO may include a plurality of protected ROs.That is the RO Response message contains at least one RO for at leastone DRM content object indicated by the RO requested message.

The RO Response message may include protected ROs in the form of“protectedRO” elements for respective DRM content objects, and eachprotectedRO includes at least one “Permission” element specifying theactual usage of the content object and at least one “constraint” elementfor restricting the permission on the usage of the content object. Thatis, the “constraint” may be dependent on the “permission.” For example,the permission element may be one of “play”, “display”, “execute”,“print”, and “export”, and the constraint element may be one of “count”,“timed-count”, “datetime”, “interval”, “individual”, and “system.”

In a case that the broker server 400 and the RIs 610 to 630 areauthenticated with each other, the RO Response messages transmitted bythe broker server 400 and the RIs 610 to 630 carry the protected ROswithout additional security process. If the broker server 400 and theRIs 610 to 630 are not authenticated with each other (i.e., Insecurecommunication is performed), a Mutual authentication process may beperformed between the broker server 400 and the RIs 610 to 630.

The digital signature of the broker server 400 is verified as followingprocess. In a case that the mobile terminal 200 is authenticated (i.e.,a secure communication is established), the broker server 400 transmitsan RO Response message carrying only its own signature to the mobileterminal 200. On the other hand, if the mobile terminal 200 is notauthenticated (i.e., an insecure communication is established), thebroker server 400 verifies the digital signatures of the RIs 610 to 630and transmits an RO Response message containing its signature as well asthe digital signature of the RIs 610 to 630. In the case that thedigital signatures of all the RIs 610 to 630 are contained in the ROResponse message. The message format of the RO Response message may bechanged.

Preferably, when it fails to acquire any of the multiple ROs requestedby the mobile terminal 200, the broker server 400 or a specific RIreports the information on the RO failed to receive and the reason ofthe RO acquisition failure. If the acquisition failure message isreceived from the broker server 400, the mobile terminal 200 outputs analert such as an acquisition failure information or acquisition failurealarm.

In the above manner, the broker server 400 performs a mutualauthentication by verify the digital signatures of the mobile terminal200 and the RIs 610 to 630. This kind of architecture relieves themobile terminal 200 from verifying every RI individually since themobile terminal 200 verifies only the digital signature of the brokerserver 400.

Although not shown in FIG. 7, the mobile terminal may perform a webtransaction with the broker server 400 after transmitting the ROAPTrigger Request message. During the web transaction, the broker server400 receives the purchase information of the content objects from therespective RIs 610 and 630 and publishes the information on a webpage,and the mobile terminal displays the purchase information on the displayunit. At this time, the user can decide the values of the permissionsand constraints of the ROs corresponding to the content objects.

For example, if the broker server 400 publishes the purchase informationon a web page, the mobile terminal 200 composes a purchase list inresponse to the user input for selecting the final content objects to bepurchased. At this time, the broker server 400 generates at least oneROAP Trigger Request message on the basis of the purchase list receivedfrom the mobile terminal 200 and transmits the ROAP Trigger Requestmessage to at least one RI.

Although the broker server-involved batch RO acquisition architectureand method are described with reference to FIGS. 6 and 7, the presentinvention is not limited thereto. For example, the batch RO acquisitionarchitecture and method can be accomplished by embedding thefunctionality of the broker server within the respective RIs without anadditional broker server. A batch RO acquisition system and methodwithout engagement of the broker server is described hereinafter.

FIG. 8 is a schematic block diagram illustrating a batch RO acquisitionsystem according to another exemplary embodiment of the presentinvention. In this embodiment, the batch RO acquisition system isdeployed in a ring network topology.

Referring to FIG. 8, a mobile terminal 200 transmits an RO Requestmessage to the first RI 810. The RO Request message may contain at leastone RI URL including the URL of the first RI 810 that provides the CIDsof the content objects to be purchased.

The mobile terminal 200 extracts at least one CID and at least one RIURL which provides the CID and transmits the RO Request message to theRI URL (in FIG. 8, the URL of the first RI 810).

In the case that multiple RI URLs are contained in the RO Requestmessage, one of the RI URLs is selected according to a preset userconfiguration. That is, the RI URL can be selected randomly, in an orderof preset priority, in an ascendant or descendent order of the RIs, orthe like.

The first RI 810 received the RO Request message performs the followingprocesses:

1) Authentication of Device

2) If pass, creating ROs.

3) Adding signature

4) Creating RO Response

That is, the first RI 810 authenticates the mobile terminal 200 and, ifthe mobile terminal passes the authentication process, generates atleast one RO and adds its signature to the RO. The authenticationprocess can be performed using the OCSP.

The authentication can be performed in an initial registration of themobile terminal or in response to a request of the RI. For example, in acase that the DRM time of a specific content object is different fromthe device time of the RI (i.e., the difference between the DRM time andthe RI time is greater than a predetermined value), the RI may requestre-authentication. The authentication of the mobile terminal may beperformed by exchanging the OCSP Request message and OCSP Responsemessage between the RI and an OCSP Responder.

Next, the first RI 810 creates an RO Response message containing theinformation on the RO and its signature. The first RI 810 transmits theRO Request message to one of the RI URLs (i.e., the second RI 820)contained in the RO Request message. At this time, the first RI 810 maytransmit the RO Response message together with the RO Request message.The first RI 810 may delete its URL from the RO Request message beforetransmitting the RO Request message to the second RI 820.

If the RO Request message is received, the second RI 820 performs thefollowing processes:

1) Authentication of Device

2) Authentication of previous RI

3) If pass, creating ROs

4) Adding signature (or replacing signature)

5) Creating RO Response

That is, if the RO Request message is received, the second RI 820performs authentication of the mobile terminal 200 and, if the mobileterminal passes the authentication test, creates at least one RO andadds its signature to the RO. The second RI 820 performs theauthentication of the first RI 810.

The authentication process on the mobile terminal 200 may skipped. Thatis, since the mobile terminal 200 is authenticated by the first RI 810,the second RI 820 skips the authentication of the mobile terminal 200 intrust of the authentication by the first RI 810. In this case, the firstRI 810 informs the second RI 820 of the authentication of the mobileterminal 200, and the second RI 820 checks whether the RO Requestmessage is received from the mobile terminal 200 or another RI.

The second RI 820 may add its signature to the RO or replace thesignature of the first RI 810 with its own signature.

Next, the second RI 820 creates an RO Response message containing theinformation of the RO and at least one signature. Sequentially, thesecond RI 820 transmits the RO Request message to one of RI URLscontained in the RO Request message (i.e., the third RI 830). At thistime, the RO Response message is transmitted together with the RORequest message. The second RI 820 may delete its URL from the RORequest message before transmitting to the third RI 830.

The third RI 830 and N'th RI 840 perform the identical procedure carriedout by the second RI 820. The N'th RI 840 recognizes that there is noother RI to transmit the RO Request message and transmits an RO Responsemessage containing the ROs issued by previous RIs and/or by itself andat least one signature to the mobile terminal 200. The N'th RI 840 canrecognize itself as the final RI by checking the RI URLs contained inthe RO Request message since the RO Request message received by thefinal RI containing only one RI URL (when the previous RIs delete theirRI URL from the RO Request message). Also, the N'th RI 840 can recognizeitself as the final RI by checking the signatures added in the ROResponse message.

FIG. 9 is a schematic block diagram illustrating an aggregation ROacquisition system according to another exemplary embodiment of thepresent invention. In this embodiment, the batch RO acquisition systemis implemented with a push mechanism.

Referring to FIG. 9, a mobile terminal 200 transmits an RO Requestmessage to a first RI 910. The RO Request message contains at least oneRI URL including the URL of the first RI 910 that provides CIDs of thecontent objects to be purchased.

The mobile terminal 200 extracts at least one CID and at least one RIURL which provides the CID of the content object to be purchased andtransmits the RO Request message to the RI URL (in FIG. 9, the URL ofthe first RI 910).

In the case that multiple RI URLs are contained in the RO Requestmessage, one of the RI URLs is selected according to a preset userconfiguration. That is, the RI URL can be selected randomly, in an orderof preset priority, in an ascendant or descendent order or the RIs, orthe like.

The first RI 910 receives the RO Request message transmitted by themobile terminal 200 and performs authentication of the mobile terminal200 on the basis of the RO Request message. If the mobile terminal 200passes the authentication test, the first RI 910 creates a RO Responsemessage containing at least one RO and its signature and transmits theRO Response message to the mobile terminal 200. The first RI 910 alsotransmits the RO Request message to a second RI 920 with reference tothe RI URLs contained in the RO Request message. At this time, the firstRI 910 may delete its URL from the RO Request message.

If the RO Request message is received from the first RI 910, the secondRI 920 performs authentication of the mobile terminal 200. If the mobileterminal 200 passes the authentication test, the second RI 920 createsan RO Response message containing at least one RO and its signature tothe mobile terminal 200. The second RI 920 also may performauthentication of the first RI 910. Next, the second RI 920 transmitsthe RO Request message to one of the RI URLs contained in the RO Requestmessage (in this embodiment, the third RI 930). At this time, the secondRI 920 may delete its URL from the RO Request message.

The authentication of the mobile terminal 200 may be skipped. That is,since the mobile terminal 200 is authenticated by the first RI 910, thesecond RI 920 skips the authentication of the mobile terminal 200 intrust of the authentication by the first RI 910. In this case, the firstRI 910 informs the second RI 920 of the authentication of the mobileterminal 200, and the second RI 920 checks whether the RO Requestmessage is received from the mobile terminal 200 or another RI. Thesecond RI 920 may add its signature to the RO or replace the signatureof the first RI 910 with its own signature.

The third RI 930 and N'th RI 940 perform the identical procedure carriedout by the second RI 920. The N'th RI 940 recognizes that there is noother RI to transmit the RO Request message and transmits an RO Responsemessage. The N'th RI 940 can recognize itself as the final RI bychecking the RI URL remained in the RO Request message in which other RIURLs are deleted by previous RIs.

Although not shown in FIGS. 8 and 9, at least one of the RIs verifies apublic key certificate of the mobile terminal using the OCSP. The OCSPis a protocol to verify the public key certificate of the mobileterminal 200 in real time. That is, the OCSP checks whether the publickey certificate of the mobile terminal is aborted.

In this embodiment, a heterogeneous RI environment is assumed in whichthe different types of RIs are deployed. In a case that the mobileterminal is not registered with the RIs according to a typicalregistration standard, or a re-registration of the mobile terminal isrequired, the ROAP registration process should be performed. In thestandard, an ROAP registration protocol and a registration protocol isspecified.

The standard specifies that the registration protocol is executed asfollowing situation.

1) at first contact

2) update of the exchanged security information

3) DRM time

That is, the registration protocol is executed when the mobile terminalattempts to initially contact to the RI server, the exchanged securityinformation is required to be updated, and the DRM time (secure time) isinaccurate.

In the heterogeneous RI environment according to an exemplaryembodiment, the mobile terminal can register with different types of RIssimultaneously. The mobile terminal also initiates the registrationprotocol whenever attempting the registration with the respective RIs.As described above, the mobile terminal may initiate the registrationprotocol only one time with the first RI and skip the initiation of theregistration protocol with other RIs.

In order to execute the registration protocol, the mobile terminal andthe RI server exchanges messages such as “Device Hello”, “RI Hello”,“Registration Request”, and Registration Response.” The mobile terminaland the RI perform the registration procedure by exchanging the abovemessages. These messages are formatted as shown in Tables 3 to 6.

TABLE 3 <element name=“deviceHello” type=“roap:DeviceHello”/><complexType name=“DeviceHello”>  <annotation>    <documentationxml:lang=“en”>     Message sent from Device to RI to establish an RIContext.   </documentation>  </annotation> <complexContent>  <extensionbase=“roap:Request”>    <sequence>     <element name=“version”type=“roap:Version”/>     <element name=“deviceID”type=“roap:Identifier”      maxOccurs=“unbounded”/>     <elementname=“supportedAlgorithm” type=“anyURI”      minOccurs=“0”maxOccurs=“unbounded”/>     <element name=“extensions”type=“roap:Extensions”      minOccurs=“0”/>    </sequence>  </extension>  </complexContent> </complexType>

Table 3 shows an exemplary “Device Hello” message firstly sent by themobile terminal in the ROAP registration protocol.

TABLE 4 <element name=“riHello” type=“roap:RIHello”/> <complexTypename=“RIHello”>  <annotation>   <documentation xml:lang=“en”>    Messagesent from RI to Device in response to a deviceHello message.  </documentation>  </annotation>  <complexContent>   <extensionbase=“roap:Response”>     <sequence minOccurs=“0”>      <elementname=“selectedVersion” type=“roap:Version”/>      <element name=“riID”type=“roap:Identifier”/>      <element name=“selectedAlgorithm”type=“anyURI” maxOccurs=“unbounded”        minOccurs=“0”/>      <elementname=“riNonce” type=“roap:Nonce”/>      <elementname=“trustedAuthorities”       type=“roap:KeyIdentifiers”minOccurs=“0”/>      <element name=“serverInfo” type=“base64Binary”minOccurs=“0”/>      <element name=“extensions” type=“roap:Extensions”minOccurs=“0”/>    </sequence>    <attribute name=“sessionId”type=“string”/>   </extension>  </complexContent> </complexType><complexType name=“KeyIdentifiers”>  <sequence minOccurs=”0”maxOccurs=“unbounded”>   <element name=“keyIdentifier”type=“roap:KeyIdentifier”/>  </sequence> </complexType>

Table 4 shows an exemplary “RI Hello” message which is sent in responseto the “Device Hello” message.

TABLE 5 <element name=“registrationRequest”type=“roap:RegistrationRequest”/> <complexTypename=“RegistrationRequest”>  <annotation>   <documentationxml:lang=“en”>    Message sent from Device to RI to requestregistration.   </documentation>  </annotation>  <complexContent>   <extension base=“roap:Request”>     <sequence>      <elementname=“nonce” type=“roap:Nonce”/>      <element name=“time”type=“roap:dateTimeOrUndefined”/>     <element name=“certificateChain”type=“roap:CertificateChain”      minOccurs=“0”/>     <elementname=“trustedAuthorities” type=“roap:KeyIdentifiers”     minOccurs=“0”/>     <element name=“serverInfo” type=“base64Binary”minOccurs=“0”/>     <element name=“extensions” type=“roap:Extensions”minOccurs=“0”/>     <element name=“signature” type=“base64Binary”/>   </sequence>    <attribute name=“sessionId” type=“string”use=“required”/>   </extension>  </complexContent> </complexType>

Table 5 shows an exemplary “Registration Request” message which istransmitted from the mobile terminal to the RI for requestingregistration.

TABLE 6 <element name=“registrationResponse”type=“roap:RegistrationResponse”/> <complexTypename=“RegistrationResponse”>  <annotation>   <documentationxml:lang=“en”>    Message sent from RI to Device in response to aregistrationRequest message.   </documentation>  </annotation> <complexContent>   <extension base=“roap:Response”>    <sequenceminOccurs=“0”>     <element name=“riURL” type=“anyURI”/>     <elementname=“certificateChain” type=“roap:CertificateChain”     minOccurs=“0”/>     <element name=“ocspResponse”type=“base64Binary” minOccurs=“0”      maxOccurs=“unbounded”/>    <element name=“extensions” type=“roap:Extensions” minOccurs=“0”/>    <element name=“signature” type=“base64Binary”/>    </sequence>   <attribute name=“sessionId” type=“string”/>   </extension> </complexContent> </complexType>

Table 6 shows an exemplary “Registration Response” message which istransmitted in response to the “Registration Request” message.

Although not shown in FIGS. 8 and 9, if an error occurs at a specific RI(e.g., RO Request or RO Response message is lost), it is preferred forthe mobile terminal to display the information on the erroneous RI orerroneous content object and the reason of the error on the displayscreen.

As described above, the RO acquisition procedure is explained inassociation with the operations of the mobile terminal, RIs, and brokerserver. The present invention is not limited thereto. For example, theRO acquisition procedure can be applied between the client terminal suchas personal computer and a server, or between two servers.

As described above, the rights object acquisition method and system ofthe present invention enables a mobile terminal to acquire multiplerights objects in a batch processing manner, resulting in improvement ofuser convenience. Also, the rights object acquisition method and systemof the present invention can be implemented in association with aquantity discount system so as to improve sales of the digital contents,resulting in development of contents business.

Also, the rights object acquisition method and system of the presentinvention introduces a broker server which provides a single servicepoint for verifying digital signatures of a mobile terminal and RIs soas to reduce complicated authentication processes between a mobileterminal and every RIs, thereby relieving the processing load of themobile terminal, improving performance of the mobile terminal, andreducing multiple RO acquisition time.

Also, the rights object acquisition method and system of the presetinvention enables a mobile terminal to acquire multiple ROs withouttransmitting RO Request messages to all RIs issuing the ROs, resultingin reducing traffic redundancy.

Although the present disclosure has been described with an exemplaryembodiment, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims.

What is claimed is:
 1. A rights object acquisition method comprising:transmitting a rights object request message requesting one or morerights objects of content objects from a mobile terminal to a rightsissuer; creating, at the rights issuer, a rights object response messagecontaining at least one of rights objects indicated by the rights objectrequest message and at least one signature in response to the rightsobject request message; and transmitting the rights object responsemessage from the rights issuer to the mobile terminal.
 2. The rightsobject acquisition method of claim 1, wherein the rights object requestmessage comprises one or more content identifiers and at least one ofURLs of rights issuers, each rights issuer providing at least one ofrights objects indicated by the rights object request message.
 3. Therights object acquisition method of claim 2, further comprisingtransmitting the rights object request message from the rights issuer toat least one other rights issuer.
 4. The rights object acquisitionmethod of claim 2, further comprising transmitting the rights objectresponse message from the rights issuer to at least one other rightsissuer.
 5. The rights object acquisition method of claim 4, wherein therights object response message comprises information of at least onerights issuer.
 6. The rights object acquisition method of claim 2,further comprising transmitting the rights object request message andthe rights object response message from the rights object server to atleast one other rights object server.
 7. The rights object acquisitionmethod of claim 1, further comprising authenticating, at the rightsobject server, the mobile terminal and adding a signature in the rightsobject response message.
 8. The rights object acquisition method ofclaim 7, further comprising replacing, at the rights issuer, thesignature contained in the rights object response message with asignature or the rights issuer.
 9. A rights object acquisition methodcomprising: transmitting a rights object request message requesting oneor more rights objects of content objects from a mobile terminal to afirst rights issuer; creating, at the first rights issuer, a firstrights object response message containing at least one of rights objectsindicated by the rights object request message and at least onesignature; transmitting the rights object request message and the firstrights objects response message from the first rights issuer to a secondrights issuer designated in the rights object request message; creating,at the second rights issuer, a second rights object response messagecontaining at least one of rights objects indicated by the rights objectrequest message and at least one signature; and transmitting, when noother rights issuer designated in the rights object request message isremained, the second rights object response message from the secondrights issuer to the mobile terminal.
 10. The rights object acquisitionmethod of claim 9, further comprising authenticating, at the firstrights issuer, the mobile terminal.
 11. The rights object acquisitionmethod of claim 10, further comprising adding, at the first rightsissuer, a signature of the first rights issuer in the rights objectrequest message.
 12. The rights object acquisition method of claim 11,further comprising adding, at the second rights issuer, a signature ofthe second rights issuer in the rights object request message.
 13. Therights object acquisition method of claim 12, further comprisingauthenticating, at the second rights issuer, the first rights issuer.14. A rights object acquisition method comprising: transmitting a rightsobject request message requesting one or more rights objects of contentobjects form a mobile terminal to a first rights issuer; transmittingthe rights object request message from the first rights issuer to asecond rights issuer designated in the rights object request message;transmitting a rights object response message containing at least one ofthe rights objects indicated by the rights object request message andthe first rights issuer's signature from the first rights issuer to themobile terminal; and transmitting a right object response messagecontaining at least one of the rights objects indicated by the rightsobject request message and the first rights issuer's signature from thefirst rights issuer to the mobile terminal.
 15. The rights objectacquisition method of claim 14, further comprising authenticating, atthe first rights issuer, the mobile terminal.
 16. The rights objectacquisition method of claim 14, further comprising authenticating, atthe second rights issuer, the first rights issuer.
 17. A rights objectacquisition method comprising: transmitting a first rights objectrequest message requesting one or more rights objects of contentsobjects from a mobile terminal to a broker server; transmitting thesecond rights object request message from the broker server to at leastone rights issuer; transmitting a first rights object response messagecontaining at least one of rights objects indicated by the rights objectrequest message and a signature of the rights issuer from the individualrights issuer to the broker server; and transmitting a second rightsobject response message created on the basis of the first rights objectresponse message from the broker server to the mobile terminal.
 18. Therights object acquisition method of claim 17, further comprisingauthenticating, at the broker server, the mobile terminal.
 19. Therights object acquisition method of claim 18, further comprisingverifying, at the broker server, the signature of the individual rightsissuer.
 20. The rights object acquisition method of claim 18, whereinthe first rights object request message comprises at least one contentidentifier and at least one address of the rights issuer by contentidentifier.
 21. The rights object acquisition method of claim 20,wherein transmitting the second rights object request message comprises:recognizing, at the broker server, the at least one rights issuer on thebasis of the at least one address; creating at least one second rightsobject request message destined to the at least one address; andtransmitting the at least one second rights object request message tothe individual rights issuer.
 22. A rights object acquisition systemcomprising: a mobile terminal which requests and acquires at least onerights object of at least one content object in a batch processingmanner; and a server which performs authentication of the mobileterminal and provides the mobile terminal with the at least one rightsobjects in a batch processing manner.
 23. The rights object acquisitionsystem of claim 22, wherein the server comprises at least one rightsissuer for issuing the at least one rights objects requested by themobile terminal.
 24. The rights object acquisition system of claim 22,further comprising at least one rights issuer for issuing at least onerights object requested by the mobile terminal, and the server is abroker server for providing interoperability service between the mobileterminal and the at least one rights issuer.
 25. The rights objectacquisition system of claim 24, wherein the broker server recognizes theat least one rights issuer by objects right and transmits a rightsobject request message to the at least one rights issuer.
 26. The rightsobject acquisition system of claim 23, wherein the at least one rightsissuer transmits the rights object request message to another rightsissuer.
 27. The rights object acquisition system of claim 23, whereinthe at least one rights issuer transmits a rights object responsemessage created in response to the rights object request message toanother rights issuer.
 28. The rights object acquisition system of claim27, wherein the rights object response message contains information onat least one rights issuer.
 29. The rights object acquisition system ofclaim 23, wherein the at least one rights issuer transmits the rightsobject request message to another rights issuer and a rights objectresponse message created in response to the rights object requestmessage to another rights issuer.
 30. The rights object acquisitionsystem of claim 23, wherein the at least one rights issuer authenticatesthe mobile terminal and creates a rights object response messagecontaining a signature of the rights issuer.
 31. The rights objectacquisition system of claim 30, wherein the rights issuer replaces thesignature contained in the rights object response message with thesignature of the rights issuer.
 32. The rights object acquisition systemof claim 22, wherein the mobile terminal transmits a rights objectrequest message containing at least one content identifier and at leastone address of at least one rights issuer by content identifier to theserver.